v8.19.0

Compare Source

node --import=@​sentry/node/import app.js

- **feat(node): Do not exit process by default when other `onUncaughtException` handlers are registered in
  `onUncaughtExceptionIntegration` (#​11532)**

In v8, we will no longer exit the node process by default if other uncaught exception handlers have been registered by
the user.

- **Better handling of transaction name for errors**

We improved the way we keep the transaction name for error events, even when spans are not sampled or performance is
disabled.

- feat(fastify): Update scope `transactionName` when handling request (#​11447)
- feat(hapi): Update scope `transactionName` when handling request (#​11448)
- feat(koa): Update scope `transactionName` when creating router span (#​11476)
- feat(sveltekit): Update scope transactionName when handling server-side request (#​11511)
- feat(nestjs): Update scope transaction name with parameterized route (#​11510)

##### Removal/Refactoring of deprecated functionality

- feat(core): Remove `getCurrentHub` from `AsyncContextStrategy` (#​11581)
- feat(core): Remove `getGlobalHub` export (#​11565)
- feat(core): Remove `Hub` class export (#​11560)
- feat(core): Remove most Hub class exports (#​11536)
- feat(nextjs): Remove webpack 4 support (#​11605)
- feat(vercel-edge): Stop using hub (#​11539)

##### Other Changes

- feat: Hoist `getCurrentHub` shim to core as `getCurrentHubShim` (#​11537)
- feat(core): Add default behaviour for `rewriteFramesIntegration` in browser (#​11535)
- feat(core): Ensure replay envelopes are sent in order when offline (#​11413)
- feat(core): Extract errors from props in unkown inputs (#​11526)
- feat(core): Update metric normalization (#​11518)
- feat(feedback): Customize feedback placeholder text color (#​11417)
- feat(feedback): Maintain v7 compat in the @​sentry-internal/feedback package (#​11461)
- feat(next): Handle existing root spans for isolation scope (#​11479)
- feat(node): Ensure tracing without performance (TWP) works (#​11564)
- feat(opentelemetry): Export `getRequestSpanData` (#​11508)
- feat(opentelemetry): Remove otel.attributes in context (#​11604)
- feat(ratelimit): Add metrics rate limit (#​11538)
- feat(remix): Skip span creation for `OPTIONS` and `HEAD` requests. (#​11149)
- feat(replay): Merge packages together & ensure bundles are built (#​11552)
- feat(tracing): Adds span envelope and datacategory (#​11534)
- fix(browser): Ensure pageload trace remains active after pageload span finished (#​11600)
- fix(browser): Ensure tracing without performance (TWP) works (#​11561)
- fix(nextjs): Fix `tunnelRoute` matching logic for hybrid cloud (#​11576)
- fix(nextjs): Remove Http integration from Next.js (#​11304)
- fix(node): Ensure isolation scope is correctly cloned for non-recording spans (#​11503)
- fix(node): Make fastify types more broad (#​11544)
- fix(node): Send ANR events without scope if event loop blocked indefinitely (#​11578)
- fix(tracing): Fixes latest route name and source not updating correctly (#​11533)
- ref(browser): Move browserTracing into browser pkg (#​11484)
- ref(feedback): Configure font size (#​11437)
- ref(feedback): Refactor Feedback types into @​sentry/types and reduce the exported surface area (#​11355)

#### 8.0.0-beta.0

This release failed to publish correctly. Use 8.0.0-beta.1 instead.

#### 8.0.0-alpha.9

This is the eighth alpha release of Sentry JavaScript SDK v8, which includes a variety of breaking changes.

Read the [in-depth migration guide](./MIGRATION.md) to find out how to address any breaking changes in your code.

##### Important Changes

- **feat: Add @​sentry-internal/browser-utils (#​11381)**

A big part of the browser-runtime specific exports of the internal `@sentry/utils` package were moved into a new package
`@sentry-internal/browser-utils`. If you imported any API from `@sentry/utils` (which is generally not recommended but
necessary for some workarounds), please check that your import statements still point to existing exports after
upgrading.

- **feat: Add loader file to node-based SDKs to support ESM monkeypatching (#​11338)**

When using ESM, it is necessary to use a "loader" to be able to instrument certain third-party packages and Node.js API.
The server-side SDKs now ship with a set of ESM loader hooks, that should be used when using ESM. Use them as follows:

```sh

v8.18.0

Compare Source

Important Changes

• ref: Deprecate enableTracing (12897)

The enableTracing option has been deprecated and will be removed in the next major version. We recommend removing it
in favor of the tracesSampleRate and tracesSampler options. If you want to enable performance monitoring, please set
the tracesSampleRate to a sample rate of your choice, or provide a sampling function as tracesSampler option
instead. If you want to disable performance monitoring, remove the tracesSampler and tracesSampleRate options.

Other Changes

• feat(node): Expose exclude and include options for ESM loader (#​12910)
• feat(browser): Add user agent to INP standalone span attributes (#​12896)
• feat(nextjs): Add experimental_captureRequestError for onRequestError hook (#​12885)
• feat(replay): Bump rrweb to 2.25.0 (#​12478)
• feat(tracing): Add long animation frame tracing (#​12646)
• fix: Cleanup hooks when they are not used anymore (#​12852)
• fix(angular): Guard ErrorEvent check in ErrorHandler to avoid throwing in Node environments (#​12892)
• fix(inp): Ensure INP spans have correct transaction (#​12871)
• fix(nestjs): Do not make SentryTraced() decorated functions async (#​12879)
• fix(nextjs): Support automatic instrumentation for app directory with custom page extensions (#​12858)
• fix(node): Ensure correct URL is passed to ignoreIncomingRequests callback (#​12929)
• fix(otel): Do not add otel.kind: INTERNAL attribute (#​12841)
• fix(solidstart): Set proper sentry origin for solid router integration when used in solidstart sdk (#​12919)
• fix(sveltekit): Add Vite peer dep for proper type resolution (#​12926)
• fix(tracing): Ensure you can pass null as parentSpan in startSpan* (#​12928)
• ref(core): Small bundle size improvement (#​12830)

Work in this release was contributed by @​GitSquared and @​mcous. Thank you for your contributions!

Bundle size 📦

v8.17.0

Compare Source

• feat: Upgrade OTEL deps (#​12809)
• fix(nuxt): Add module to build:transpile script (#​12843)
• fix(browser): Allow SDK initialization in NW.js apps (#​12846)

v8.16.0

Compare Source

Important Changes

• feat(nextjs): Use spans generated by Next.js for App Router (#​12729)

Previously, the @sentry/nextjs SDK automatically recorded spans in the form of transactions for each of your top-level
server components (pages, layouts, ...). This approach had a few drawbacks, the main ones being that traces didn't have
a root span, and more importantly, if you had data stream to the client, its duration was not captured because the
server component spans had finished before the data could finish streaming.

With this release, we will capture the duration of App Router requests in their entirety as a single transaction with
server component spans being descendants of that transaction. This means you will get more data that is also more
accurate. Note that this does not apply to the Edge runtime. For the Edge runtime, the SDK will emit transactions as it
has before.

Generally speaking, this change means that you will see less transactions and more spans in Sentry. You will no
longer receive server component transactions like Page Server Component (/path/to/route) (unless using the Edge
runtime), and you will instead receive transactions for your App Router SSR requests that look like
GET /path/to/route.

If you are on Sentry SaaS, this may have an effect on your quota consumption: Less transactions, more spans.

• - feat(nestjs): Add nest cron monitoring support (#​12781)

The @sentry/nestjs SDK now includes a @SentryCron decorator that can be used to augment the native NestJS @Cron
decorator to send check-ins to Sentry before and after each cron job run:

import { Cron } from '@​nestjs/schedule';
import { SentryCron, MonitorConfig } from '@​sentry/nestjs';
import type { MonitorConfig } from '@​sentry/types';

const monitorConfig: MonitorConfig = {
  schedule: {
    type: 'crontab',
    value: '* * * * *',
  },
  checkinMargin: 2, // In minutes. Optional.
  maxRuntime: 10, // In minutes. Optional.
  timezone: 'America/Los_Angeles', // Optional.
};

export class MyCronService {
  @​Cron('* * * * *')
  @​SentryCron('my-monitor-slug', monitorConfig)
  handleCron() {
    // Your cron job logic here
  }
}

Other Changes

• feat(node): Allow to pass instrumentation config to httpIntegration (#​12761)
• feat(nuxt): Add server error hook (#​12796)
• feat(nuxt): Inject sentry config with Nuxt addPluginTemplate (#​12760)
• fix: Apply stack frame metadata before event processors (#​12799)
• fix(feedback): Add missing h import in ScreenshotEditor (#​12784)
• fix(node): Ensure autoSessionTracking is enabled by default (#​12790)
• ref(feedback): Let CropCorner inherit the existing h prop (#​12814)
• ref(otel): Ensure we never swallow args for ContextManager (#​12798)

v8.15.0

Compare Source

• feat(core): allow unregistering callback through on (#​11710)
• feat(nestjs): Add function-level span decorator to nestjs (#​12721)
• feat(otel): Export & use spanTimeInputToSeconds for otel span exporter (#​12699)
• fix(core): Pass origin as referrer for lazyLoadIntegration (#​12766)
• fix(deno): Publish from build directory (#​12773)
• fix(hapi): Specify error channel to filter boom errors (#​12725)
• fix(react): Revert back to jsxRuntime: 'classic' to prevent breaking react 17 (#​12775)
• fix(tracing): Report dropped spans for transactions (#​12751)
• ref(scope): Delete unused public getStack() (#​12737)

Work in this release was contributed by @​arturovt and @​jaulz. Thank you for your contributions!

v8.14.0

Compare Source

Important Changes

• feat(nestjs): Filter 4xx errors (#​12695)

The @sentry/nestjs SDK no longer captures 4xx errors automatically.

Other Changes

• chore(react): Remove private namespace JSX (#​12691)
• feat(deps): bump @​opentelemetry/propagator-aws-xray from 1.25.0 to 1.25.1 (#​12719)
• feat(deps): bump @​prisma/instrumentation from 5.16.0 to 5.16.1 (#​12718)
• feat(node): Add registerEsmLoaderHooks option (#​12684)
• feat(opentelemetry): Expose sampling helper (#​12674)
• fix(browser): Make sure measure spans have valid start timestamps (#​12648)
• fix(hapi): Widen type definitions (#​12710)
• fix(nextjs): Attempt to ignore critical dependency warnings (#​12694)
• fix(react): Fix React jsx runtime import for esm (#​12740)
• fix(replay): Start replay in afterAllSetup instead of next tick (#​12709)

Work in this release was contributed by @​quisido. Thank you for your contribution!

v8.13.0

Compare Source

Important Changes

• feat(nestjs): Add Nest SDK This release adds a dedicated SDK for NestJS (@sentry/nestjs)
  in alpha state. The SDK is a drop-in replacement for the Sentry Node SDK (@sentry/node) supporting the same set of
  features. See the docs for how to use the SDK.

Other Changes

• deps: Bump bundler plugins to 2.20.1 (#​12641)
• deps(nextjs): Remove react peer dep and allow rc (#​12670)
• feat: Update OTEL deps (#​12635)
• feat(deps): bump @​prisma/instrumentation from 5.15.0 to 5.15.1 (#​12627)
• feat(node): Add context info for missing instrumentation (#​12639)
• fix(feedback): Improve feedback error message (#​12647)

v8.12.0

Compare Source

Important Changes

• feat(solid): Remove need to pass router hooks to solid integration (breaking)

This release introduces breaking changes to the @sentry/solid package (which is currently out in alpha).

We've made it easier to get started with the solid router integration by removing the need to pass use* hooks
explicitly to solidRouterBrowserTracingIntegration. Import solidRouterBrowserTracingIntegration from
@sentry/solid/solidrouter and add it to Sentry.init

import * as Sentry from '@​sentry/solid';
import { solidRouterBrowserTracingIntegration, withSentryRouterRouting } from '@​sentry/solid/solidrouter';
import { Router } from '@​solidjs/router';

Sentry.init({
  dsn: '__PUBLIC_DSN__',
  integrations: [solidRouterBrowserTracingIntegration()],
  tracesSampleRate: 1.0, //  Capture 100% of the transactions
});

const SentryRouter = withSentryRouterRouting(Router);

• feat(core): Return client from init method (#​12585)

Sentry.init() now returns a client directly, so you don't need to explicitly call getClient() anymore:

const client = Sentry.init();

• feat(nextjs): Add deleteSourcemapsAfterUpload option (#​12457)

This adds an easy way to delete sourcemaps immediately after uploading them:

module.exports = withSentryConfig(nextConfig, {
  sourcemaps: {
    deleteSourcemapsAfterUpload: true,
  },
});

• feat(node): Allow to configure maxSpanWaitDuration (#​12610)

Adds configuration option for the max. duration in seconds that the SDK will wait for parent spans to be finished before
discarding a span. The SDK will automatically clean up spans that have no finished parent after this duration. This is
necessary to prevent memory leaks in case of parent spans that are never finished or otherwise dropped/missing. However,
if you have very long-running spans in your application, a shorter duration might cause spans to be discarded too early.
In this case, you can increase this duration to a value that fits your expected data.

Other Changes

• feat(feedback): Extra check for iPad in screenshot support (#​12593)
• fix(bundle): Ensure CDN bundles do not overwrite window.Sentry (#​12580)
• fix(feedback): Inject preact from feedbackModal into feedbackScreenshot integration (#​12535)
• fix(node): Re-throw errors from koa middleware (#​12609)
• fix(remix): Mark isRemixV2 as optional in exposed types. (#​12614)
• ref(node): Add error message to NodeFetch log (#​12612)

Work in this release was contributed by @​n4bb12. Thank you for your contribution!

v8.11.0

Compare Source

Important Changes

• feat(core): Add parentSpan option to startSpan* APIs (#​12567)

We've made it easier to create a span as a child of a specific span via the startSpan* APIs. This should allow you to
explicitly manage the parent-child relationship of your spans better.

Sentry.startSpan({ name: 'root' }, parent => {
  const span = Sentry.startInactiveSpan({ name: 'xxx', parentSpan: parent });

  Sentry.startSpan({ name: 'xxx', parentSpan: parent }, () => {});

  Sentry.startSpanManual({ name: 'xxx', parentSpan: parent }, () => {});
});

Other Changes

• feat(node): Detect release from more providers (#​12529)
• fix(profiling-node): Use correct getGlobalScope import (#​12564)
• fix(profiling-node) sample timestamps need to be in seconds (#​12563)
• ref: Align @sentry/node exports from framework SDKs. (#​12589)

Bundle size 📦

v8.10.0

Compare Source

Important Changes

• feat(remix): Migrate to opentelemetry-instrumentation-remix. (#​12110)

You can now simplify your remix instrumentation by opting-in like this:

const Sentry = require('@​sentry/remix');

Sentry.init({
  dsn: YOUR_DSN
  // opt-in to new auto instrumentation
  autoInstrumentRemix: true,
});

With this setup, you do not need to add e.g. wrapExpressCreateRequestHandler anymore. Additionally, the quality of the
captured data improves. The old way to use @sentry/remix continues to work, but it is encouraged to use the new setup.

Other Changes

• feat(browser): Export thirdPartyErrorFilterIntegration from @sentry/browser (#​12512)
• feat(feedback): Allow passing tags field to any feedback config param (#​12197)
• feat(feedback): Improve screenshot quality for retina displays (#​12487)
• feat(feedback): Screenshots don't resize after cropping (#​12481)
• feat(node) add max lineno and colno limits (#​12514)
• feat(profiling) add global profile context while profiler is running (#​12394)
• feat(react): Add React version to events (#​12390)
• feat(replay): Add url to replay hydration error breadcrumb type (#​12521)
• fix(core): Ensure standalone spans respect sampled flag (#​12533)
• fix(core): Use maxValueLength in extra error data integration (#​12174)
• fix(feedback): Fix scrolling after feedback submission (#​12499)
• fix(feedback): Send feedback rejects invalid responses (#​12518)
• fix(nextjs): Update @​rollup/plugin-commonjs (#​12527)
• fix(node): Ensure status is correct for http server span errors (#​12477)
• fix(node): UnifygetDynamicSamplingContextFromSpan (#​12522)
• fix(profiling): continuous profile chunks should be in seconds (#​12532)
• fix(remix): Add nativeFetch support for accessing request headers (#​12479)
• fix(remix): Export no-op as captureRemixServerException from client SDK (#​12497)
• ref(node) refactor contextlines to use readline (#​12221)

Work in this release was contributed by @​AndreyKovanov and @​kiliman. Thank you for your contributions!

v8.9.2

Compare Source

• fix(profiling): Update exports so types generate properly (#​12469)

v8.9.1

Important changes

• feat(solid): Add Solid SDK

  This release adds a dedicated SDK for Solid JS in alpha state with instrumentation for
  Solid Router and a custom ErrorBoundary. See the
  package README for how to use
  the SDK.

Other changes

• feat(deps): bump @​opentelemetry/instrumentation-express from 0.40.0 to 0.40.1 (#​12438)
• feat(deps): bump @​opentelemetry/instrumentation-mongodb from 0.44.0 to 0.45.0 (#​12439)
• feat(deps): bump @​opentelemetry/propagator-aws-xray from 1.24.1 to 1.25.0 (#​12437)
• feat(nextjs): Allow for suppressing warning about missing global error handler file (#​12369)
• feat(redis): Add cache logic for redis-4 (#​12429)
• feat(replay): Replay Web Vital Breadcrumbs (#​12296)
• fix: Fix types export order (#​12404)
• fix(astro): Ensure server-side exports work correctly (#​12453)
• fix(aws-serverless): Add op to Otel-generated lambda function root span (#​12430)
• fix(aws-serverless): Only auto-patch handler in CJS when loading awslambda-auto (#​12392)
• fix(aws-serverless): Only start root span in Sentry wrapper if Otel didn't wrap handler (#​12407)
• fix(browser): Fix INP span creation & transaction tagging (#​12372)
• fix(nextjs): correct types conditional export ordering (#​12355)
• fix(replay): Fix guard for exception event (#​12441)
• fix(vue): Handle span name assignment for nested routes in VueRouter (#​12398)

Work in this release was contributed by @​soch4n. Thank you for your contribution!

v8.9.0

This release failed to publish correctly, please use 8.9.1 instead.

v8.8.0

Compare Source

• feat: Upgrade OTEL dependencies (#​12388)

This upgrades the OpenTelemetry dependencies to the latest versions and makes OTEL use import-in-the-middle v1.8.0.
This should fix numerous issues with using OTEL instrumentation with ESM.

High level issues fixed with OTEL + ESM:

• incompatibilities with using multiple loaders, commonly encountered while using tsx or similar libraries.
• incompatibilities with libraries that use duplicate namespace exports like date-fns.
• incompatibilities with libraries that use self-referencing namespace imports like openai.
• incompatibilities with dynamic export patterns like exports with function calls.
• ENOENT: no such file or directory bugs that libraries like discord.js
  surface.

If you are still encountering issues with OpenTelemetry instrumentation and ESM, please let us know.

• deps: Bump Sentry bundler plugins to version 2.18.0 (#​12381)
• feat: Add thirdPartyErrorFilterIntegration (#​12267)
• feat(core): Filter out error events with exception values and no stacktraces, values, or types (#​12387)
• feat(core): Ignore additional common but inactionable errors (#​12384)
• feat(deps): Bump @​opentelemetry/propagator-aws-xray from 1.3.1 to 1.24.1 (#​12333)
• feat(deps): Bump @​sentry/cli from 2.31.2 to 2.32.1 (#​12332)
• feat(redis): Support mget command in caching functionality (#​12380)
• feat(vercel-edge): Export core integrations from Vercel edge SDK (#​12308)
• fix(browser): Fix idle span ending (#​12306)
• fix(browser): Fix parenthesis parsing logic for chromium (#​12373)
• fix(browser): Fix types export path for CJS (#​12305)
• fix(feedback): Override TriggerLabel Option (#​12316)
• fix(feedback): Wait for document to be ready before doing autoinject (#​12294)
• fix(nextjs): Fix memory leak (#​12335)
• fix(nextjs): Fix version detection and option insertion logic for clientTraceMetadata option (#​12323)
• fix(nextjs): Update argument name in log message about sentry property on Next.js config object (#​12366)
• fix(node): Do not manually finish / update root Hapi spans. (#​12287)
• fix(node): Fix virtual parent span ID handling & update create-next-app E2E test (#​12368)
• fix(node): Skip capturing Hapi Boom responses v8. (#​12288)
• fix(performance): Fix LCP not getting picked up on initial pageload transaction by setting reportAllChanges to true
  (#​12360)
• fix(replay): Avoid infinite loop of logs (#​12309)
• fix(replay): Ignore old events when manually starting replay (#​12349)
• ref(browser): Ensure idle span ending is consistent (#​12310)
• ref(profiling): unref timer (#​12340)

v8.7.0

Important Changes

• feat(react): Add TanStack Router integration (#​12095)

  This release adds instrumentation for TanStack router with a new tanstackRouterBrowserTracingIntegration in the
  @sentry/react SDK:

  import * as Sentry from '@​sentry/react';
  import { createRouter } from '@​tanstack/react-router';
  
  const router = createRouter({
    // Your router options...
  });
  
  Sentry.init({
    dsn: '___PUBLIC_DSN___',
    integrations: [Sentry.tanstackRouterBrowserTracingIntegration(router)],
    tracesSampleRate: 1.0,
  });

Other Changes

• fix(nextjs): Do not hide sourceMappingURL comment on client when nextConfig.productionBrowserSourceMaps: true is
  set (#​12278)

v8.6.0

Important Changes

• feat(metrics): Add timings method to metrics (#​12226)

  This introduces a new method, metrics.timing(), which can be used in two ways:

  1. With a numeric value, to simplify creating a distribution metric. This will default to second as unit:

  Sentry.metrics.timing('myMetric', 100);

  2. With a callback, which will wrap the duration of the callback. This can accept a sync or async callback. It will
     create an inactive span around the callback and at the end emit a metric with the duration of the span in seconds:

  const returnValue = Sentry.metrics.timing('myMetric', measureThisFunction);

• feat(react): Add Sentry.reactErrorHandler (#​12147)

  This PR introduces Sentry.reactErrorHandler, which you can use in React 19 as follows:

  import * as Sentry from '@​sentry/react';
  import { hydrateRoot } from 'react-dom/client';
  
  ReactDOM.hydrateRoot(
    document.getElementById('root'),
    <React.StrictMode>
      <App />
    </React.StrictMode>,
    {
      onUncaughtError: Sentry.reactErrorHandler(),
      onCaughtError: Sentry.reactErrorHandler((error, errorInfo) => {
        // optional callback if users want custom config.
      }),
    },
  );

  For more details, take a look at the PR. Our
  documentation will be updated soon!

Other Changes

• feat(sveltekit): Add request data to server-side events (#​12254)
• fix(core): Pass in cron monitor config correctly (#​12248)
• fix(nextjs): Don't capture suspense errors in server components (#​12261)
• fix(tracing): Ensure sent spans are limited to 1000 (#​12252)
• ref(core): Use versioned carrier on global object (#​12206)

v8.5.0

Compare Source

Important Changes

• feat(react): Add React 19 to peer deps (#​12207)

This release adds support for React 19 in the @sentry/react SDK package.

• feat(node): Add @sentry/node/preload hook (#​12213)

This release adds a new way to initialize @sentry/node, which allows you to use the SDK with performance
instrumentation even if you cannot call Sentry.init() at the very start of your app.

First, run the SDK like this:

node --require @​sentry/node/preload ./app.js

Now, you can initialize and import the rest of the SDK later or asynchronously:

const express = require('express');
const Sentry = require('@​sentry/node');

const dsn = await getSentryDsn();
Sentry.init({ dsn });

For more details, head over to the
PR Description of the new feature. Our docs will be updated
soon with a new guide.

Other Changes

• feat(browser): Do not include metrics in base CDN bundle (#​12230)
• feat(core): Add startNewTrace API (#​12138)
• feat(core): Allow to pass custom scope to captureFeedback() (#​12216)
• feat(core): Only allow SerializedSession in session envelope items (#​11979)
• feat(nextjs): Use Vercel's waitUntil to defer freezing of Vercel Lambdas (#​12133)
• feat(node): Ensure manual OTEL setup works (#​12214)
• fix(aws-serverless): Avoid minifying Module._resolveFilename in Lambda layer bundle (#​12232)
• fix(aws-serverless): Ensure lambda layer uses default export from ImportInTheMiddle (#​12233)
• fix(browser): Improve browser extension error message check (#​12146)
• fix(browser): Remove optional chaining in INP code (#​12196)
• fix(nextjs): Don't report React postpone errors (#​12194)
• fix(nextjs): Use global scope for generic event filters (#​12205)
• fix(node): Add origin to redis span (#​12201)
• fix(node): Change import of @prisma/instrumentation to use default import (#​12185)
• fix(node): Only import inspector asynchronously (#​12231)
• fix(replay): Update matcher for hydration error detection to new React docs (#​12209)
• ref(profiling-node): Add warning when using non-LTS node (#​12211)

v8.4.0

Compare Source

Important Changes

• feat(nextjs): Trace pageloads in App Router (#​12157)

If you are using Next.js version 14.3.0-canary.64 or above, the Sentry Next.js SDK will now trace clientside pageloads
with React Server Components. This means, that client-side errors like
Error: An error occurred in the Server Components render., which previously didn't give you much information on how
that error was caused, can now be traced back to a specific error in a server component.

• feat(angular): Add Support for Angular 18 (#​12183)

This release guarantees support for Angular 18 with @sentry/angular.

Other Changes

• feat(deps): Bump @​opentelemetry/instrumentation-aws-lambda from 0.41.0 to 0.41.1 (#​12078)
• fix(metrics): Ensure string values are interpreted for metrics (#​12165)

v8.3.0

Compare Source

Important Changes

• Better Node Framework Span Data

This release improves data quality of spans emitted by Express, Fastify, Connect, Koa, Nest.js and Hapi.

• feat(node): Ensure connect spans have better data (#​12130)

• feat(node): Ensure express spans have better data (#​12107)

• feat(node): Ensure fastify spans have better data (#​12106)

• feat(node): Ensure hapi spans have better data (#​12140)

• feat(node): Ensure koa spans have better data (#​12108)

• feat(node): Ensure Nest.js spans have better data (#​12139)

• feat(deps): Bump @​opentelemetry/instrumentation-express from 0.38.0 to 0.39.0 (#​12079)

• feat(node): No-code init via --import=@​sentry/node/init (#​11999)

When using Sentry in ESM mode, you can now use Sentry without manually calling init like this:

 SENTRY_DSN=https://[email protected]/0 node --import=@​sentry/node/init app.mjs

When using CommonJS, you can do:

 SENTRY_DSN=https://[email protected]/0 node --require=@​sentry/node/init app.js

Other Changes

• chore: Align and update MIT license dates (#​12143)
• chore: Resolve or postpone a random assortment of TODOs (#​11977)
• doc(migration): Add entry for runWithAsyncContext (#​12153)
• docs: Add migration docs to point out that default import does not work (#​12100)
• docs(sveltekit): process.env.SENTRY_AUTH_TOKEN (#​12118)
• feat(browser): Ensure browserProfilingIntegration is published to CDN (#​12158)
• feat(google-cloud): Expose ESM build (#​12149)
• feat(nextjs): Ignore Prisma critical dependency warnings (#​12144)
• feat(node): Add app.free_memory info to events (#​12150)
• feat(node): Do not create GraphQL resolver spans by default (#​12097)
• feat(node): Use node: prefix for node built-ins (#​11895)
• feat(replay): Use unwrapped setTimeout to avoid e.g. angular change detection (#​11924)
• fix(core): Add dsn to span envelope header (#​12096)
• fix(feedback): Improve feedback border color in dark-mode, and prevent auto-dark mode when a theme is picked (#​12126)
• fix(feedback): Set optionOverrides to be optional in TS definition (#​12125)
• fix(nextjs): Don't put undefined values in props (#​12131)
• fix(nextjs): Fix legacy configuration method detection for emitting warning (#​12136)
• fix(node): Ensure fetch/http breadcrumbs are created correctly (#​12137)
• fix(node): Update @prisma/instrumentation from 5.13.0 to 5.14.0 (#​12081)
• ref(node): Add log for running in ESM/CommonJS mode (#​12134)
• ref(node): Handle failing hook registration gracefully (#​12135)
• ref(node): Only show instrumentation warning when tracing is enabled (#​12141)

Work in this release contributed by @​pboling. Thank you for your contribution!

v8.2.1

Compare Source

• fix(aws-serverless): Fix build of lambda layer (#​12083)
• fix(nestjs): Broaden nest.js type (#​12076)

v8.2.0

Compare Source

• feat(redis-cache): Create cache-span with prefixed keys (get/set commands) (#​12070)
• feat(core): Add beforeSendSpan hook (#​11886)
• feat(browser): Improve idle span handling (#​12065)
• fix(node): Set transactionName for unsampled spans in httpIntegration (#​12071)
• fix(core): Export Scope interface as Scope (#​12067)
• fix(core): Avoid looking up client for hasTracingEnabled() if possible (#​12066)
• fix(browser): Use consistent timestamps (#​12063)
• fix(node): Fix check for performance integrations (#​12043)
• ref(sveltekit): Warn to delete source maps if Sentry plugin enabled source maps generation (#​12072)

v8.1.0

Compare Source

This release mainly fixes a couple of bugs from the initial 8.0.0 release. In addition to the changes below, we
updated some initially missed points in our migration guides and documentation.

• feat(aws-serverless): Fix tree-shaking for aws-serverless package (#​12017)
• feat(node): Bump opentelemetry instrumen